Method for dynamic creation of customized tour guides

ABSTRACT

The invention is a method and system of creating and delivering dynamic and customized tour guides to a user through an electronic device. The system takes into account factors including the speed, direction of movement, and geographical location of a user&#39;s electronic device along with a user&#39;s preferences, and calculating a timeframe in which a user will be in proximity to a point of interest to create and deliver a customized and tailored tour guide experience. The system and method is scalable and allows a multitude of individual users simultaneously have individually tailored tour guides delivered to them covering a broad range of topics including architecture, history, surrounding nature, and current events of points of interest along a user&#39;s pre-defined or predicted user route.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present patent application claims priority to U.S. patentapplication Ser. No. 15/607,408 filed on May 26, 2017, which claimspriority to U.S. Provisional Patent Application Ser. No. 62/343,079,filed May 30, 2016.

FIELD OF THE INVENTION

The present invention relates to the field of tour guides. Moreparticularly to the field of dynamically created tour guides that arecustomized to the route of the tour guide's user.

BACKGROUND ART

Currently available Travel Guides (trip, tour, museum) are pre-createdstatic materials in the text, image, audio or video forms, which providethe information to the end user without taking into account thesituation, state, user preferences and needs. The Guides usually aredelivered via printed mediums (books, booklets, magazines), electronicmediums (CD, DVD, MPx formats), or personal computing devices(computers, laptops, smart devices, wearables) in a shape ofapplications or computer programs. The most advanced travel guides takeready manually prepared information material, make the user followcertain instructions (for example, follow geographical route), andtrigger the material delivery based on the user location on this route.This is very limited, because:

a) User cannot receive the guide wherever they go (route on the road,museum, trail) they have to follow certain predefined route with thepredefined speed to get the guide.b) The big cities, museums, popular tourist destinations are somewhatcovered with the rigid static guides, but majority of the routes(especially via road travel) are completely uncovered.c) User will receive the same guide information following the same routeagain no new content will be served.d) No user and situational context is taken into account, despite thedifference in the user preferences, schedule, experience, needs, theguide will stay the same.

Because of this limitation, nonhuman guiding experience in travel isfragmented and non-satisfactory for the end users.

The invention addresses the gap and provide dynamic flexible runtimeguides with the 100% of route coverage wherever the user goes, takinginto account user needs, preferences and schedule, and serving new,relevant data every time of use.

SUMMARY OF THE INVENTION

A method of creation and delivering the travel guide comprises of thefollowing steps: a) Information gathering: data about objects to becovered in the guide is either manually loaded, obtained from the 3rdsystems, crawled on the Internet, or crowdsourced; b) Informationprocessing: gathered objects data is processed, sorted, unified andformatted in a way to be used in the guide, and stored (optionally); c)Figuring out the needs of the client: client requirements are obtainedeither by explicit user input, and/or by implicit learning about Clienthistorical behavior and preferences, and learnings on the clusteredclient groups; d) Guide creation: based on the requesting clientrequirements, the guide is machine created from the processedinformation; e) Guide serving: guide is delivered to the client (inrequested format audio, video, text) per client request and situationcontext.

The travel guide is created automatically based on any location of auser, any user's travel destination(s) and any user travel route, i.e.,regardless, from where or to where, the user goes they would receive theunique travel guide. Current travel guide solutions, eithersoftware/hardware based, or paper, are able to deliver travel guides forspecific locations and routes only, thus their coverage is limited. Thisinvention provides a solution which is dynamic and covers the entireEarth. Also, the guide is customizable for user needs and travel plans.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will now be discussed in further detail below withreference to the accompanying figures in which:

FIG. 1 is a high level view of guide creation according to the presentinvention.

FIG. 2 shows multiple paths of formation of a single example story graphaccording to the present invention.

FIG. 3 shows a Guide Graph according to the present invention.

FIG. 4 shows how the electronic device performs path selection within aGuide Graph.

FIG. 5 shows part of the method of the present invention beingimplemented as a tour guide application on an electronic device.

FIG. 6 demonstrates one manner in which the overall time to conveyinformation conveyed in a story graph is determined according to thepresent invention.

FIG. 7 is a flow chart of the present method of creating and deliveringa dynamic customized tour guide to a user according to the presentinvention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Terminology

“Passing (by),” as used herein with reference to the user passing (by) aplace of interest (POI), is defined as a calculated position by thepresent invention of the user, the calculated position of the user beingrelative to the center of the POI, the calculated position equating towhen the difference between the coordinates of a user device locationand the coordinates of the POI location, on the map, is zero) thecorresponding point of interest. If the user's device does not pass thecenter of the POI, the present invention takes the lowest value obtainedto infer that the user has passed the central point of the POI andtherefore is moving, or at least beginning to move, away from the POI.Such a determination may be made, e.g., via any graphical software whichbegins to show a trough-like graph. It is noted that, in addition to theinformation disclosed herein, several currently known methods exist forsuch geometrical determinations. The range of the user to the center ofa point of interest is determined using the following factor: The guideshould begin talking about the POI before the POI is approached, and theguide finishes right after (or some time after after) the user passesthe lowest value obtained to infer that the user has passed the centralpoint of the POI. Therefore, passing (by) can also mean that the user isa distance from the central point of the POI, and therefore “passing(by)” does not necessarily require an exact moment in time. In suchcases, the issue is how to determine the starting point and ending pointof “passing (by)”. This is performed by taking into account thefollowing factors: (1) the speed of the user; (2) an estimated distanceto the lowest value obtained between user and center of POI; 3) theduration of the POI description in time (e.g., there can be storyalternatives talking about the same POI); (4) the locations of otherPOIs, depending on how far the user is from the other POIs (if the useris nearby another POI, additional descriptions of those POIs can beadded if time permits. Selecting the story alternative (based on anotherPOI nearby) is performed via a formula based on the user's estimatedduration of travel between POI1 and POI2. The POI story duration alsotakes into account user preferences that impact the customization of theguide). If the minimum of a target POI story's duration (storyalternative with minimum duration) is greater than or equal to theuser's estimated duration of travel between POI1 and POI2, then one ofthe other POI's stories may be skipped (as both wont fit the timeconstraints). If the maximum of a target POI story duration (storyalternative with maximum duration) is less than or equal to the user'sestimated duration of travel between POI1 and POI2, then the guide mayselect additional POIs to describe in order to fill in the silence. Itis also noted that a POI itself may be not a point, but an area—forexample, if a user enters a new country, or is exploring a nationalpark, the guide may present a story about the area, not just a specificpoint in it. In this case, the story may be given as soon as a userenters the area's border, thus any moment within the area (for example,when the user is walking through an area where POIs having centralpoints are located far from each other, the guide may fill in thesilence with general descriptions of the area.

POI: Point Of Interest certain object (landmark, restaurant, hotel,vista, etc) on the map (and earth) which could be interesting for userto visit/observe.

Route: Instructions/description on the way for the user to reach fromlocation A to location B.

User: An individual smartphone user with location data.

Customer: Business owner whose POI/business is promoted via the systemwith coupons and/or tickets.

GPS: Global Positions System is the connection to the smartphone.

GPS Integration: Is the method of connecting GPS data to specificsmartphone operating systems.

Photos/Video: Is the feature on smartphones that allows users to takeand upload photos.

Social Media Credentials: The credentials users used to login to othersocial media sites, such as Facebook, Twitter, LinkedIn, etc. Thesecredentials usually are user names and passwords.

Social Media Promotion: A nonconventional promotion channel via socialmedia sites with the viral effects.

Text Messages: Is the feature allowing mobile phones to receive shortmessages SMS or text messages via a wireless network.

Deal Record: A record in the system's cloud Database storing informationabout certain promoted deal (discount coupons).

Ticket Record: A record in the system's cloud Database storinginformation about certain promoted tickets to visit certain attractionPOI.

OATH2: secure protocol between clients and servers for user login.

Frequent Roadtripper: A person travelling by car at least once per monthor often for the distances 75+ miles.

The main concept of this innovation is that, instead of being static andpredefined, Guide is dynamically created from the bulk of availableinformation (online databases, internet, web application apis, onlinebooks, press (magazines), web sites, crowdsourced user uploadedinformation, video and audio data) based on the current use casecontext, and then served dynamically as well depending on the userneeds, user behavior, preferences, environmental state and situationalcontext. The guide of the present invention is able to cover alllocations on Earth, rather than a selective few locations (i.e., theguide scales, while the prior art cannot)) For example:

Patty, who likes art, wine and sea shore, travels from San Francisco toSanta Barbara, and follows the Rt 1 road. Leaves at 9 am on Saturday.Taking this data as an input, the system implementing the subject Methodwould:

i) Take Patty's travel route, find the Places of Interest (POIs) andGeographical Objects (GO) along the route using the electronic Maps(proprietary or 3rd party, like Google Maps, Yelp, etc);

ii) Gather the information about the POIs and GOs crawling thedatabases, internet, websites (POIs sites, news, online magazines)online web applications (like Wikipedia, foursquare, etc);

iii) Process the information using Natural Language Processing methodsfor the relevance, quality and context correlation;

iv) Create the Guide graph with the portions of processed data andmachine generated content structured and connected into a shape of thestory blocks;

v) Construct the Guide runtime from the processed information storyblocks taking into account Patty's preferences (that she likes art, wineand sea shore), Patty's schedule (when she leaves, expected time whenshe would be at certain locations), Patty historical behaviors (when shelikes to have a lunch, how long she drives without stops usually, whatelse she like to discover on the route), and inputs from the othersimilar users behaviors (user who likes wine stopped at this winery);

vi) Serve the guide to Patty on the go dynamically adjusting to hermoving speed, route changes, stops and requests (like: Patty moves withthe speed 60 mph, at the city A along her route there are 5 interestingplaces wineries and art galleries to tell about, but as she moves byquickly there is enough time to tell only about 2, most priorital. IfPatty slows down to 30 mph moving through the town, the stories of all 5POIs will be told. If Patty changes the route, new data for the guide isloaded and served and also the sequence of the story is changed. IfPatty asks “what is this landmark on the right”, guide searches theinformation about the place by the name and location, reconstructs thewhole story and tells Patty about the landmark).

Guide Content data Preprocessing

1. Object/POI data correlation: as data is gathered from the differentsources, it contains multiple information pieces which might be relatedto the same POI/object. So the system performs identification of theobjects and matching (correlation) of the information pieces. POI/objectgeographic location, name, description, attributes are used to do thematching. Matching rules can be as strict (exact match), so weaklocations within certain distance, some keywords are matching, someattributes, similar phrases in the description. Level of correlation(strict or weak) is flexible and defined by particular use caserequirements.

2. Object/POI data cleanup and sorting: once all the data is identifiedand correlated with particular object/POIs, data cleanup is performed:a. data, which didn't find the object/POI to belong to, is removed; b.duplicate information is consolidated; c. low quality data (likefragmented pieces) is deleted.

Guide Element “Story” Creation Story Graph

For each object to be included into the Guide (POI, fact, etc) the StoryGraph is created, based on the obtained data from the multiple sources.Story Graph structured as the Nodes, connected together into the graph,with single or multiple paths between nodes, and when any path isfollowed, the connected story about the object can be retrieved. i.e.pieces of text information, and/or audio/video information connectedtogether in a such way, that following the connections from start to anyend of the graph, the user can read/hear/see logically and semanticallyconnected story.

1. Nodes: logically and semantically complete text, audio, video piecesof the information.

1.1. Two types of nodes:

1.1.1. Story node: Content for the node extracted from the obtained dataabout the object (POI, fact, etc). Object data is structurally analysed,broke down into the parts, attributed with the semantic keywords,priorities, etc. Nodes could be text, audio and/or video.

1.1.2. Service node: Content for the node is generated for the servicepurpose: connect the story nodes together, give a user the storypreview, etc, create nice start/ending of the story. For example “ Nowlet me tell you about the sports events in the city”.

1.2. How the node content is created for the Story Node:

1.2.1. Text Content:

1.2.1.1. Text is parsed for the paragraph, sentences, headers extracted.

1.2.1.2. Using Natural Language processing algorithms based on thekeyword and text patterns extraction and their correlation, high levelmeaning of the piece is detected, and corresponding attribute isattached to the piece. For example, for the piece “The city was foundedin 1845 by the state governor” the method detects the pattern “wasfounded, <year>”, attributes the piece with the tags “generic, history”.These tags are used to correlate the pieces of the text and structurethem in the right way.

1.2.1.3. Identified pieces are stored as a Nodes attributed with thetags of original source, predecessor and successor Node IDs (if the Nodeis extracted from the text), semantic tags (what topic the node relatesto, what it talks about), node length (duration when converted into theaudio piece), priorities, etc.

1.2.2. Audio content:

1.2.2.1. Audio title and attributes are analysed and high level audiorelevance is detected (based on the keywords and text patterns).

1.2.2.2. Audio content is converted from speech to text using the speechrecognition engine, and the resulted text is recorded. The text thenparsed using Natural Language processing techniques to identify keywordsand text patterns, and then, based on the analysis results, audio pieceis attributed with the corresponding semantic keywords.

1.2.3. Video content:

1.2.3.1. Video title and attributes are analysed and high level audiorelevance is detected (based on the keywords and text patterns).

1.2.3.2. Audio row is extracted and content is converted from speech totext using the speech recognition engine, and the resulted text isrecorded. The text then parsed using Natural Language processingtechniques to identify keywords and text patterns, and then, based onthe analysis results, audio piece is attributed with the correspondingsemantic keywords.

1.2.4. Inappropriate/irrelevant content:

1.2.4.1. During the parsing & analysis process the content is checked tosee if it is appropriate/relevant.

1.2.4.1.1. Inappropriate words, phrases identified (bad, etc.).

1.2.4.1.2. Irrelevant content identified for example, we expect museumwith this name, and based on the keyword analysis, we see “shop”,“shopping mall”, “apparel”.

1.2.4.2. Inappropriate/irrelevant content is cleaned up.

2. Story Graph: the Nodes, connected together in a way representing theorder, sequence, priority of the individual pieces of information forthe guide execution.

2.1. The graph vertices reference the Nodes.

2.2. The graph edges show how Nodes should be connected with each otherin the story, and also carry the attributes of the graph transitions:

2.2.1. Priority of the transition;

2.2.2. Duration of the piece ahead;

2.2.3. Semantic key attributes of the branch (about what the branchwould be telling, like “history, sport”);

2.2.4. Number of the nodes ahead;

2.2.5. Etc.

2.3. The Nodes in the graph are connected in the way, that each pathfrom the head to any node represent the connected semantically completestory.

2.4. To construct the graph, the following factors are taken intoaccount:

2.4.1. Original order of the Nodes extracted from the source (like whatpiece of text goes after another).

2.4.2. Attributes of the nodes, with the focus of the Node topic (whatit talks about) and duration, and also the nodes priorities (morefactors can be accounted for).

2.5. Once the graph structure is identified in terms of the order andconnections of the Story Nodes, Service Nodes are generated and insertedto smoothly connect the pieces of the information with each other:

2.5.1. Including announcing header/topic of the next story node;

2.5.2. Announcing start, continuation, end of the story;

2.5.3. Extracting, summarizing upcoming information of the next storynode(s) and condensing it in a shorter concise node (for the purpose ofthe duration reduction for the shorter guides, mostly, so the long pathcan be altered with the shorter node when there is no time).

Guide Creation from the Story Graphs

The overall guide structure is the following: Individual guide elementsnodes, connected together into the guide graph:

1. Guide Graph Nodes: elements, which reference/contain the Story Graphsof individual unique objects:

1.1. Story Graphs of Obtained content : POIs, facts, service data, etcinformation comprising the representation of the objects included intothe guide.

1.2. Service Guide Nodes: created or generated content which purpose isto connect the data from the individual Story Graphs nodes into thesmooth relevant story: for example: “We finished the story of SantaBarbara downtown. Next, will talk about Santa Barbara beaches, startingfrom Butterfly beach”.

2. Guide Graph: the Guide Graph Nodes, connected together in a wayrepresenting the order, sequence, priority of the Guide Graph Nodes forthe guide execution.

2.1. The graph vertices reference the Guide Graph Nodes (individualStory Graphs and/or Service Guide Nodes).

2.2. The graph edges show how Guide Graph Nodes should be connected witheach other in the story, and also carry the attributes of the graphtransitions:

2.2.1. Priority of the transition;

2.2.2. Duration of the piece ahead in time;

2.2.3. Semantic key attributes of the branch (about what the branchwould be telling, like “history, sport”);

2.2.4. Number of the nodes ahead;

2.2.5. The type of the node ahead Story Graph, another Guide Graph, orService Guide Node.

3. To summarize, the guide is a multilevel hierarchy of graphs, whichreference the content and the rules of this content execution in theguide. The depth (recursion level) in the graph can vary.

Templates

Once the Story Graph/Guide Graph is created, Templates for theGuide/Guide Story retrieval are generated: set of the paths for theGuide retrieval depending on the request types. Templates allow to speedup the guide retrieval for particular use case: for example, if theperson is interested in certain subject, like history, or nature; orneed to retrieve the shortest or longest story.

Guide Retrieval & Execution

Guide Retrieval

1. Client makes a request to the guide service, providing therequirements for the guide. a. Guide subject: trip from A to B, “aroundmy location”, tour in the museum (like Expressionist Exhibition), localnews, etc.; b. Geo parameters: location, route; c. User preferences:what user like (history, art), what is user type, behavior specific.

2. Based on the client inputs the method collects the source information(see Guide Content Raw Data Gathering section).

3. Then the method searches for the Guide Graphs fitting the request, orgenerates a new Guide Graph, if the one doesn't exist, along with theGuide Templates.

4. Then the appropriate Guide Template is identified/generated, andbased on the template, the specific Guide for this particular client,preferences & context is created.

5. The Guide is then delivered to the client.

Guide Execution

The guide served for the execution in fact is the reduced/adjusted GuideGraph with the content (text, audio, video) attached. Based on theruntime environment and user inputs, the client executes the guide:

1. Performs analysis of the runtime situation: a. Previously executedGuide Nodes; b. Current location, moving speed; c. Expected tourduration; d. User runtime reaction (skip, fast forward, focus onspecific themes) runtime learning.

2. Picks the Node/subgraph Node to execute following the Guide Graphbased on the runtime situation analysis, such as:

a. How many Stories the guide would be able to cover while user is closeto this location. (For example, if user moves fast, the guide would beable to tell about POI1 and POI2 while user is passing by, but if theuser moves slow, then saying guide would be able to squeeze the storiesof the other POIs);

i. Special Priority & Weight logic is used to decide, which ObjectStories will be served: Parameters accounted to make the rightprioritization:

1) Static (prior run-time): ⋅POIs ratings from external sources;⋅Roadgazer Place Rating⋅Roadgazer User Historical Date ratings (machinelearning on individual user behavior and user group clusters); ⋅POIdensity in the area; ⋅quality of the place data, defined by: data source(i.e. which APIs solutions, or crawled, or crowd-sourced, orprofessionally recorded), type (audio, video, text), amount (how much ofthe info, are there alternatives), content quality (parsing quality,etc.); ⋅other factors can be potentially added.

Processed on Server. Every place gets a list of parameters above, andevery parameter gets score S (score from 1 to 5) based on the datapre-processing and weight W (0-1) ⋅empirical factor defined and turnedduring user trials. Places prioritized based on the valueV=SUM(V1;Vn)/N=S*W, where Vn=Sn*Wn; ⋅bigger V, higher the priority.After prioritization is finished, server returns the list of tops to theclient (if saying client asked for the 20 places, then top twenty arereturned).

2) Dynamic (run-time): distance to the POI from the route or currentuser location⋅user speed⋅user moving direction⋅history of the guideroute for particular user (if user already listened to the guide on thisroute, need to pick something new).

Once client received a prioritized list of places from the server, itfilters it and alters the priority based on the dynamic factors, beforeadding to the audio tour for the user, using same score—weight approach.

b. How detailed the Story about particular Object (POI) should bedepends on the speed, user behavior and preferences (for example, ifuser likes history, talk longer in the historical section of the guide,but reduce sports).

c. If the user already read/heard/seen the story about the objectalready.

i. Special round robin method is used for the repeating routes/themes.

If the user is driving the same route multiple times, they do not wantto listen to the same information. Instead, new (or forgotten)information shall be supplied. The guide does not repeat same info twicein a row.

Instead, the following logic is applied:

There is timeout T, if the user listened to the piece of information, itshould not be played again during the next tour for time T (empiricalvalue, to be tuned with the users, now set 1 month).

There the is a time stamp (TSi)—time, associated with the each place,when it was played last time

There is a place priority, defining the places queue for particularlocation (Pi)

There a places queue available to be listen in current location Q—list,sorted according to the priorities P0>P1, and P0—the one to listen.

Simple logic : round robin with taking T into account

Active Place=Q[0];

Make the Q[1] the new head (shift the queue to the left)

Q[last]=Active Place;

This way we maintain the Priority sequence and push the already heardplaces to the end in case whole list is heard before t>T, queue willrestart in the same order. But, if the original Q was not exhaustedbefore t>T for some places i.e. not places in the list were heard byparticular user, and timeout T expires for certain points (i.e. tcurrent >=TSi+T), then the place with expired timeout is being insertedaccording its priority toward the start of the Queue.

Another logic—random places pick from the list.

3. Retrieves Node content and converts in appropriate format if needed:

a. Text to speech;

b. Audio from Video;

4. Serves the Node content to the user in text, or/and audio. or/andvideo format;

5. Retrieves the runtime situation changes and user input and goes tostep 1.

Automatic Route Itinerary Creation and Adjustment

Automatic route itinerary creation and adjustment is performed thefollowing way:

f) Information gathering : data about the objects to be included intoitinerary is either manually loaded, obtained from the 3rd systems,crawled in the Internet, or crowdsourced.

g) Information processing: gathered objects data is processed, sorted,unified and formatted in a way to be used in the guide, and stored(optionally).

h) Figuring out the needs of the client: client requirements areobtained either by explicit user input, and/or by implicit learningabout Client historical behavior and preferences, and learnings on theclustered client groups.

i) Itinerary creation: based on the requesting client requirements, theitinerary is machine created from the processed information.

j) Itinerary serving: itinerary is delivered to the client per clientrequest and situation context, in a form of the route with stops,corresponding schedule and related descriptive information.

k) Itinerary adjustment: itinerary can be changed per user explicitaction, or, when the system detects the event causing the itinerarychange, for example, schedule delay, or user route change, or additionalinformation reception by the system regarding the environment, route oruser behavior.

The road trip travelers currently manually preplan their trips inadvance, selecting places to visit, sites to see, food places to eat andrest/gas points to stop. Though, road trip travel is very different fromthe other types of travel, like by air or water, by its very dynamicnature. Road trip preplanning takes a lot of time, and, on practice, theplan doesn't work well when already on the road: schedule gets delayed,places closed, sudden passenger requests appear. Thus, it is essentialto have a method and system, which would allow as fast and robust tripitinerary creation, so runtime adjustment of this itinerary on the gobased on the changes in trip schedule and context.

Instead of making user spend time manually researching and selectingplaces/activities along their routes for the trip, the guideautomatically picks the places and activities for the travelers based onthe user preference, route and schedule, and historical learning of theuser behavior and behavior of similar types of users, and construct theschedule/itinerary for the user taking into account route, time userexpected to be at certain locations during their trip, and estimatedtime to spend at the locations.

Track how the user executes the trip and automatically correct/adjustitinerary in the case the actual situation/context/behavior does notmatch the predicted expectations, or if a new situation is discovered,suggest/take the appropriate actions on the trip adjustment.

The following steps are used for the automatic trip itinerary/plancreation, and adjustment:

1. Detecting the trip route, start date and time, and trip wishes (whatuser would like to do during the trip).

2. Using the gathered trip information, collect the place/activitiesdata along the route (similar to gathering the data for the Guide in theprevious section), process and select the places/activities could fitthe trip.

3. Knowing the time/date of the trip, trip duration from the start tothe end, distances to the places, create the itinerary adding certainplaces/activities to the route fitting the user expectations andcalculating the schedule taking into account expected time to get to theplaces/activities, time to spend at the places/activities.

4. Once the itinerary is created, let the user review and correct theitinerary (adjustments would feed the trip creation logic learning basedon the user behavior).

5. When user is executing the trip, the system tracks the actualbehavior vs plan and suggests adjustments based on the observations, oracts upon the observations.

Itinerary Creation from the List of Selected POIs/Activities

Assume that the system collected the list of the places/activities alongthe user trip route, which could be interesting for the user (same wayas the Guide does in the previous section). It is necessary to processthis data and select only few to add to the user itinerary. Thedifficulty is to fit the user pace of the travel, expectations from thetrip, and take into account time/distance to the places/activities, andhow long it might take to visit them.

The following principles are used when adding the POIs/activities:

1. Duration of the trip (plan number of stop based on the duration) forexample, if the trip is short, plan the stops around destination, ifmed-size plan several stops along the route; if long nonstop (like wholeday drive) plan only few stops for rest and food, no long stops likemuseum visits.

2. Roundtrip same day, or not if roundtrip, need to account for thereturn time adding stops.

3. Time of the day the trip starts, and expected arrival time: if tripstarts early in the morning, and allows time till the evening moreplaces/activities can add to visit; if trip starts late afternoon thestops may be only rest and food.

4. Food time: estimated time to have breakfast, lunch, dinner, andsnacks is used to add the food stops. Initially certain assumptions aremade on food time, which is later adjusted upon user behavior (forexample, usual lunch time is 12 pm-1 pm. Initially planning food stoparound this time. But learning on user behavior if the user likes tohave lunch around 2 pm, using this time to add the food stop for thefurther trips).

5. Nonstop drive duration: different people can drive nonstop fordifferent duration: for example, families with kids typically stop every2 hours for rest, families no kids every 4 hours, single adults every 6hours (travel stats). So we make assumptions how often the user wouldwant to stop during the trip based on the user type (family, kids,single) initially, and trip context, and then adjust this duration basedupon learnings on actual user behavior.

6. Correlation of the stops: some people like to visit few places in onestop, some like to distribute. The Guide learns based on actual userbehavior and take it into account when planning the trip.

7. Working hours of places/activities: the system checks the overlapbetween the activities/places working hours, and the trip schedule(expected time to arrive at the place/activity, and time needed to visitplace/activity).

8. Time to spend at the certain place/activity: differentplaces/activities require different visit time. For example, museum mayeasily take 2 h, while looking at the landmark only 15 min. Fast foodneed 15 min stop, while restaurant at least an hour. The system assumestime to spend for each place initially based on the place type (likemuseum, landmark, vista, etc.) and account for it in the trip schedule.Then we learn upon set of users behavior at the certain places (how longactually they spend there) and use this individually adjusted time tospend for the future trips.

Runtime Trip Itinerary Adjustments

When the user executes the trip, the systems tracks the actual userbehavior vs the created trip itinerary, and when mismatch is detected,or unexpected new situation, flags the event suggesting certain actions:

1. When user is late and behind the schedule situation is detected, oruser is ahead of time:

a. System recalculates new expected arrival times to theplaces/activities and destination. If it detects, that any of thosemight be closed by the new arrival time, flags the message to the userand suggest to remove/automatically removes the stops.

b. If the situation is detected that now some rest/food places aremissing (like dinner place removed as it would be closed by arrivaltime), adds new places fitting new schedule.

2. When the user changes the route on the go:

a. New route is recalculated.

b. New route is analyzed if the old stops are still applicable. If notold stops removed, new stop added based on the new route.

3. When user skips the stops, or makes new, non-planned stops: type ofthe stop is checked (for the new stops either check by location/contextor ask the user, what type of stop it is), and new stop of the type issuggested (if user skipped), or removed (if user added one already).

4. When the user asks explicitly for stops: for example, asks for foodor rest in certain amount of time the system looks up for thecorresponding place/activity, adds to the itinerary and recalculates theitinerary schedule (including the subsequences like now, with new stop,user is late for some other stop).

5. When the unexpected situation is detected: for example, user istired, or driving nonstop too long, or moves very slow/fast the systemactivates the logic for the particular situation handling and acts uponit like suggesting rest, gas stops, or detours, etc.

Primary interface of interaction with the user is Voice. Applicationasks questions clarifying the user needs, recognizes the user answers(Voice Recognition), and takes appropriate actions: for example,reroutes to certain POI, provides more information about POI, recommendsplaces to eat, etc.

Trip Route Setting and Navigation

User is able to set source and destination; application suggests route;application forward the route to 3rd party Navigation app (google maps,for example); user is using 3rd party navigation app for navigation; orapplication stays in the background and controls the route.

Trip Planning

Trip can be planned: preplanned, once user set source, destination,start date and time, and (optional) current Trip preferences (TripWishes); before the trip start, once user set destination (sourcelocation and start date/time defaults to current), and (optional)current Trip preferences (Trip Wishes); on the go, the app suggestsaddition/modification of POIs to stop, user can accept; on the go, userrequests POIs stops modifications/addition, app does the modification.

Preplanned or right before trip start:

Once user set inputs for the route (destination, and optional source,date/time, Trip Wishes), application suggests the Trip, i.e. does AutoTrip planning for the user.

Auto Trip planning is done taking into account the following:

Trip Preferences; Trip Wishes i.e. what user is interested about in thistrip (like kids attractions, or wine tour); User Preferences; or UserHistorical behavior.

Trip timing: App runs smart scheduling algorithm, taking into accounttime of the day, trip duration, POIs working time, expected user trippace (number of stops, duration, etc.).

POIs relevance for this particular user.

POIs acceptance among the travellers population with similar profile asthe user.

POIs relevance for this particular trip in terms of trip expectations,route and timing.

Once Auto Trip is suggested to the User, User can adjust it : selects(pins) the POI, and Route is adjusted to include the POI, or deselects(de-pins) and POI is removed from the route.

During the trip, application suggestions: application detects triptiming/schedule changes and suggests modifications to the route; and/oruser feedbacks, if interested, then application adjusts the route andfeeds new route to 3rd party navigation application.

During the trip, by user request: user can initiate request anytimeduring the trip addition/removal of POIs to stop; and/or once audio touris provided, after information about POI is presented, user has theoption to add POI to the route.

Points of Interest

POIs are of 4 categories: attractions (vistas, landmarks, museums, etc);food (restaurants, cafe, fast food, etc); gas stations (promoted withapp partners); or hotels.

List of POIs is provided by the system backend, which takes it from:Google POIs API; Yelp; Trip Advisor; explicitly added POI by the systemuser; and explicitly added POI by the system admin.

POI's information is retrieved from the system backend, which takes itfrom: POIs source (Google POIs API, Yelp, Trip Advisor); Wikipediamaterial for Audio Guide; Flickr pictures; Travel Magazines database; orinformation (description, reviews, ratings) provided by the systemuser/admin.

When application suggests the POIs, it is based on: trip schedule/timing(example: suggest places to eat in the places user expected to be atlunch/dinner time); learnings from the user's behavior (example: ifbefore the user picked Mexican restaurants to eat more often, the systemsuggests more Mexican restaurants); user preferences that is explicitlyinput into the application (example: user selected in the preferencesthat user likes Chinese restaurants and Mexican restaurants, so theapplication will suggest to the user these types of places to eatprimarily); user history (example: if user travels the same route again,the system does not recommend the POIs the user recently visited); orPOIs ratings and reviews (example: recommend most highly rated placesfirst).

Number of POIs to choose from is limited to a reasonable amount, so useris not drowned in tons of options. User can also search for a specificPOI and add it to the route.

Audio Guide

During the trip a user is presented with the option to listen for audioguide.

Guide topics are driven by the POIs (attractions) user is passing byduring the trip or current user location.

Guide is created dynamically during the user way: user's route isanalyzed; POIs (attractions) are retrieved along the user's route byratings, historical and cultural meaning, and reasonable distance fromeach other to fit the duration needed to listen about each POI in theguide; POIs description information is retrieved (as text); text isconverted to audio using text-to-speech; and audio is played back whenuser is passing by related POI.

Guide content (POI description) is received from: Wikipedia descriptionsof POI; Travel magazines databases; or system user/admin provided text.

Audio is created by text-to-speech operations using Google text tospeech other text to speech engines.

User can start the guide, pause the guide, stop the guide and rewind:manually from the notification curtain/lock screen, when the app is inthe background; from the application screen; or by voice.

User is given the option to listen about POI as well when manuallyselecting POI card from the list and tapping “audio playback” button.

Voice Interface

The primary way of interaction by the user with the application duringthe trip is by Voice.

Voice interface includes: speaking to the user and voice Recognition ofthe user's inputs.

Voice interaction is not free-form, but build on IVR (Interactive VoiceResponse) principles. This increases voice recognition rate and,correspondingly, voice reliability. The application asks user thequestions, and gives predefined answers variants. User responds byvoice, the response is recognized and mapped to one of the expectedanswers. Corresponding action is taken by the application. Example:application says: “In five minutes we will be passing by the turn toSanta Barbara mission. Do you want to make a stop there? Say Yes or No.”User says: “Yes”. The application says: “Response ‘yes’ received.Rerouting.”

Application will prompt user with the voice requests, in appropriatesituations.

User will be able to invoke voice interface during the trip by promptingwith the key voice launch phrase. The application in the background willstay listening for the key phrase, such as “hey Roadgazer”, etc.

User Registration

User registration will be done by promoting 3rd party logins. Mainapplication functions will be available without user login. Only foradvanced usage registration will be required. Minimum data required willinclude: approval of terms and conditions; name; and email. There isalso provision for a user profile which may include: picture, socialIDs, and user preferences. The user profile also has provision for auser trip history and links to user-created POIs.

Sharing and Posting to Social Media

The user is able to make post about POI he or she liked to social media.The user must be able to share his or her trip to social media.

Review and Rating

The user is able to review and rate specific POI. The user is able topreview the POI rating and read POI reviews. Ratings and reviews of POIsare retrieved to display.

Adding New POIs

The addition of new POI is a feature of the application. User is able toadd new POIs to the system's POI database. Each new POI request shouldhave: POI name, POI location (location is based on the central point ofthe POI, i.e., the most central point relating to the particular POI),POI picture, POI category (from a list of POI categories), and a POIdescription.

FIG. 1 is a high level view of guide creation. Information on a point ofinterest (POI) is gathered from multiple sources such as 3^(rd) partyplaces application program interfaces (APIs) S11A, from publiclyaccessible websites S11B and news sites S11C, along with informationinput by the user S11D, and databases (DBs) internal to the guidecreation system S11E. Current examples of current 3^(rd) party placeAPIs include ones belonging to Google, Foursquare, and Yelp. A currentexample of a publicly accessible includes Wikipedia.

The information gathered from S11A-E goes through an aggregator microservice S12. The aggregator micro service S12 collects the related dataand passes it through to the object processor S13. The object processorS13 gathers the information for the POI and begins parsing theinformation to create a guide. Nodes are individual images, bodies oftext, information, sentences, and paragraphs related to an individualPOI and form the object stored in the objects database (DB) S15 withkeyword story indexing S14 for quicker retrieval and formation of a tourguide. Keyword story indexing S14 provides prioritization andhierarchical information for how the individual nodes of informationshould be presented in a tour guide. Using both the keyword storyindexing S14 and the objects DB S15 a story graph with nodes S16 isformed. The keyword story indexing S14 is used to an elastic search ofthe indexed story DB S17. By elastic it is meant that the search isflexible and the resulting story graphs S18 for an individual POI arealso flexible. The elasticity of the search is required in order totailor the tour guide to the individual user's location, speed, anddirection of movement.

Rather than providing a static pre-recorded tour guide where theinformation is meted out at a set pace the present invention seeks tocreate a dynamic tour guide providing varying levels of depth and lengthof information to be provided regarding an individual POI or series ofPOIs based upon parameters including the individual user's location,speed, and direction of movement. The present invention therefore worksas a dynamic tour guide that works if the user is traveling by foot,bike, car, train, or other means of transportation. And because speed ofthe user is taken into about the information conveyed by the tour guidecan be increased or decreased based upon the predicted and measuredamount of time that the user is within the vicinity of the object.Essentially the invention uses a combination of high powered servercomputing and the breadth of information available on the internet andstorable in an internal database to provide the user a customized tourguide tailored to their interest and the amount of time they are withinthe vicinity of a point of interest.

FIG. 2 shows multiple paths of formation of a single example storygraph. In this example node N21 is a 10 second start of the story aboutthe POI. Node N22 is a 30 second generic information section of thestory of the POI. At nodes N23A, N23B, and N23C there is a firstbranching of the story of the POI. Node N23A contains historicalinformation about the POI. From node N23 the story of the POI cancontinue to any one of nodes N24A-C or any combination of those nodeseach including additional historical information about the POI. From thepath chosen through nodes N24A-C leads to node N25A which contains ageneric ending which finally leads to N26A the finish of the story aboutthe POI. Alternatively the story can follow a path from node N22 to nodeN25A and contain only generic information about the POI and a genericending of the story. An alternative path can be followed from node N22through N23B and then N24D or N24E to N25A providing generic informationabout the POI, information regarding nature surrounding or at the POIand additional information regarding the habitat, plants, or flora andthen to the generic ending finishing the story. And yet anotheralternative path goes from N22 to N23C to N24F or N24E and to N25Afocusing on news and recent stories about the POI.

The story graph allows for multiple paths between nodes of informationto be conveyed to the user. This means that the story told about a POIcan be tailored to a user's preferences; if a user prefers historicalinformation the story can follow a historical path, the same being trueif the user prefers nature or new/current events information.Furthermore the length and amount of information conveyed to the user,contained in a given path through the story graph, can vary based uponmovement speed and direction of the electronic device of the user. Ifthe movement speed is low a longer story graph path containing moreinformation is taken. If the movement speed is high then a shorter pathcontaining less information is taken. And, additionally, the systemtracks which paths of a story guide have been taken so that onsubsequent visits to the same POI then at least some differentinformation is conveyed to the user about the POI. For example, if on afirst visit historical information was provided then on a second visitnews or nature information is provided instead.

The Story Graph for each object to be included into the Tour Guide iscreated based on the obtained data from the multiple sources. StoryGraph structured as nodes, the nodes connected together forming thestory graph, with single or multiple paths between nodes, and when anypath is followed, the connected story about the object can be retrieved.Pieces of text information, and/or audio and/or video informationconnected together in such a way that following the connections fromstart to any end of the graph, the user can read, hear, and/or seelogically and semantically connected story.

Generated service nodes are the nodes containing the informationproduced by the system. Generated service nodes include connectionphrases like: “And now we will talk about the history of the city” or“This is the end of the story”. Processed content story nodes containthe information gathered from public sources but is pre-processed andstructured by the system. These contain the sentences, paragraphs,images, video, and other information gathered and collated to be theelements of the Story Graph.

FIG. 3 shows a Guide Graph. The guide graph determines what informationis conveyed to the over the entire duration of the tour guide. Theparticular example is for a road trip from San Jose, Calif. to LosAngeles, Calif. Similar to the Story Graph of FIG. 2 there are differentpaths, and therefore different information for the Guide that ispresented to the user.

The Guide starts at node N31 then proceeds to N32 conveying informationregarding the start city of San Jose. From node N32 one of four paths,in this example, are selected. The shortest path just has informationconveyed when nearing Los Angeles, Calif. contained in node N35. A nodein the Guide and in a Guide Graph may contain either a single fact orpiece of information as would be found in one of the nodes of the StoryGraph or the node in a Guide Graph contains an entire Story Graphcomprised of its own nodes.

Longer Guides involving more combinations through N31, N32, N33A, anycombination of N34A-C, N35A and N36A. Each of N33A and N34A-C eachcontain their own information, whether single parcel of information oran entire Story Graph for an individual POI. In this example node N33Acontains the information for POI 1 and N34A the information for POI 3and so on.

Alternatively another path through the Guide Graph may be choseninvolving POI2 in N33B and additional information in node N34D orinformation about Santa Barbara, Calif. in N34E. And another alternativepath through the Guide Graph going through nodes N33C and N34F, whereN34F contains a Story Graph for the city of Monterey, Calif.

Which path is taken through the Guide Graph, and thereby the content ofthe Guide, is determined by multiple factors. In the present example itdepends on what route between San Jose, Calif. and Los Angeles, Calif.the user has selected. Along that route the user selects betweenmultiple suggested POIs. The suggested POIs are selected by the system.The user selects from the suggested POIs to become part of their Guide.Some of the POIs have their own Story Graphs and the path through thatStory Graph is selected based upon the factors for path selectionoutlined above.

The POIs included in the Guide are selected automatically when the userelects to use the application in automatic mode. In automatic mode thesystem selects which POIs to present based upon availability along theroute, expressed user preference, and which POIs had previously beenpresented in order to create dynamic guides.

FIG. 4 shows how the electronic device performs path selection within aGuide Graph. The resulting Guide is an aggregation of all theinformation about the POI or set of POIs. The system delivers to theuser only specific parts of the Guide Graph based on user preferences,time available, usage history, etc. To select these parts quicklytemplates could be used. Instead of selecting individual POIs the userdesires to be delivered the user could select from preselectedtemplates, in FIG. 4 being Template 1 and Template 2. This allows theuser to quickly select between two different Guides to be presented tothe user.

FIG. 5 shows part of the method being implemented as a tour guideapplication on an electronic device. First a user enters a destinationS51. The application generates a list of possible destinations S52 basedupon the destination input by the user in step S52. Once a destinationis selected by user an overview map of the route is provided along witha scrollable list of points of interest along the route S53. Once a userselects a point of interest from the list S53 a POI page is providedwith a brief description of the POI, images and video may be provided,as well as an audio button provided to allow the description of the POIto be read to the user S54. S55 shows a navigation pane. S56 is anotification page for when the POI is arrived at and may contain textand images.

FIG. 6 demonstrates one manner in which the overall time to conveyinformation conveyed in a story graph is determine. The system uses thespeed and direction of the electronic device and determines when the POI(i.e. the central point of the POI) is within a 30° angle, according tothe user's direction of travel, of the POI. This value correlates to T1.Then, based on the same metrics, when the POI is at a 120° angleaccording to the user's direction of travel, T2 is calculated. The anglebetween the user's direction of travel relative to a central (i.e.center point of a) POI location may be determined using, e.g., a devicecompass (e.g., compasses in mobile devices, compasses in cars),alternative device location detection systems, and/or mapping softwareinformation which map the POI and device coordinates on a commoncoordinate system. Known mathematical formulas for the calculation of anangle formed (1) by two lines, (2) between two lines, and/or (3) betweentwo points, may be used. The time M for the information in the StoryGraph to be conveyed is calculated as the difference between theestimated T2 and T1. With time M being determined based on the movementof the user, this M value limits which path through a Story Graph may betaken for any given set of POIs. The time M can be actively updated andmore information may be conveyed if the speed or direction of the user/electronic device deviates significantly from the estimated calculatedvalue M. Therefore, while the user is between an angle of 30↔degreesrelative to the user's direction of travel, the value M is continuouslyand automatically being estimated, such that the user may be providedwith the most relevant descriptions based on the user's locationrelative to the POI.

FIG. 7 is a flow chart of the present method of creating and deliveringa dynamic customized tour guide to a user. The steps of the method areas follows. S701: Receiving on an electronic device an information abouta geographical location of the electronic device for creating the guide;the electronic device having a system for determining geographicallocation; the geographical location being an arbitrary location in anyplace on Earth. Further receiving an information of a speed and adirection of an electronic device movement. The geographical location ofthe electronic device, the speed of the electronic device, and thedirection of the electronic device define electronic device movementparameters. S702: Defining a topic of the guide. S703: Sending requestfrom the electronic device to a server to select information aboutpoints of interest along a route. S704: A server software selectspublicly available information related to points of interest. S705: theroute is a predefined route from a point A to a point B or wherein theroute is an estimated route based on a predictive analysis of theelectronic device movement parameters. S706: The server software selectsthe publicly available information about the points of interestaccording the topic of the guide. S707: Dynamically creating a briefdescription of each point of interest along the route based on theroute, the electronic device moment parameters, and the previouslyselected publicly available about the points of interest. S708: Thedescription having a number of words equal to M×W, where M is a durationof time in minutes while the user passing said point of interest and Wis a number words per minute, wherein M is calculated using the speed ofthe electronic device movement; creating an audio description of saidpoint of interest with M×W words. S709: Delivering the description tothe user when passing (“passing,” as used herein, is defined as acalculated position by the present invention of the user, the calculatedposition of the user being relative to the center of the POI, thecalculated position equating to when the difference between thecoordinates of a user device location and the coordinates of the POIlocation, on the map, is zero) the corresponding point of interest. Ifthe user's device does not pass the center of the POI, the presentinvention takes the lowest value obtained to infer that the user haspassed the central point of the POI and therefore is moving, or at leastbeginning to move, away from the POI. Such a determination may be made,e.g., via any graphical software which begins to show a trough-likegraph. It is noted that several currently known methods exist for suchdetermination. S701: The description, which may be based on thecalculated value, is delivered on at least one of a loudspeaker or adisplay in an audio description, a video description, or a textdescription. S711: The loudspeaker L71 or the display D72 is connectedby a wired connection to, a wireless connection to, or integrated aspart of, the electronic device.

In a preferred method of practicing the invention the information aboutthe geographical location in step S701 is a current user locationreceived from a GPS inside the electronic device.

In a preferred method of practicing the invention the defined topics ofthe guide in S702 include architecture, history, nature, or currentevents.

In a preferred method of practicing the invention in step S708 the wordsper minute used to convey information W is 150.

In a preferred method of practicing the invention starting thedelivering of the audio description of step S709 when the user is 100meters from the point of interest. The distance of the user to the pointof interest may be calculated, e.g., via the following formula andassuming the ser's coordinates on the map, U=(Xu; Yu), and the POIcoordinates on the map, POI=(Xpoi; Ypoi); the distance between twolocations, D=√{square root over ((Xpoi−Xu)²+(Ypoi−Yu)²)}; ; it is notedthat currently known online maps are able to provide this distancebetween 2 points themselves. Therefore the above is merely an example.

In a preferred method of practicing the invention the informationstorage is a server containing pre-selected data about each of thepoints of interest

In a preferred method of practicing the invention the pre-selected datahas nodes that are standalone pieces of comprehensive content that canbe delivered as a sentence or paragraph and wherein the pre-selecteddata has edges that are connections between the nodes and represent theorder, sequence, and priority of individual pieces of information forthe brief description to be dynamically generated from (FIGS. 1-4).

In a preferred method of practicing the invention the preplanned routeof S705 has at least a start point A and at least a selected end point Band is determined by the first user using a third party navigationapplication which determines the preplanned route.

In a preferred method of practicing the invention the route in S705 maybe nearly instantly calculated using third-party maps & navigationsoftware, e.g., Google Maps, and based on the electronic device'smovement parameters, which may be sent to and combined in a processor ofthe present invention.

In a preferred method of practicing the invention the publicly availableinformation of S704 includes websites, publicly available applicationinterfaces (APIs) and information previously stored on the server. In apreferred method of practicing the invention the publicly availableinformation of S704 includes data in text, photo, audio and videoformats.

The system and method while described from the perspective of a singleuser works on a large scale with many individually customized travelguide for a multitude of individual users having a different locationand moving in a different direction. The speed at which guides arecreated and the number of simultaneous user guide creation requests thatcan simultaneously be processed is hardware limited. The system andmethod is scalable and is limited in number of individual guides beingcreated by the host hardware for its implementation. Host hardwareincludes central processing units (CPUs), random access memory (RAM),non-transitory computer readable mediums (hard drive disks [HDDs], solidstate drives [SSDs]), and the electronic devices of the users whichinclude smartphones, tablets, smart glasses, and vehicle infotainmentsystems.

In a preferred method of practicing the invention the serversimultaneously supports at least one thousand individually customizedtravel guides for at least one thousand individual users, each of theone thousand different users having separate and distinct electronicdevice movement parameters.

In a preferred method of practicing the invention the brief descriptionof S707 for each POI is at least 30 seconds. In a preferred method ofpracticing the invention the brief description of S707 for each POI isat least 10 seconds.

In a preferred method of practicing the invention creating the briefdescription in S707 of each point of interest is less than 1 sec.

In a preferred method of practicing the invention creating the briefdescription in S707 of each point of interest is less than 30 sec.

In a preferred method of practicing the invention the point of interestin S703 is a city, a site of historic significance, a restaurant, aplace of lodging, a museum, a geographical area, or other waypoint alongthe route.

In a preferred method of practicing the invention the description inS708 is smaller than or equal to a total information about each point ofinterest that the server has.

The logic of the method of the present invention is as follows:

Step 1. Publicly available information is collected about POI(s). Therecan be multiple sources of information, multiple POIs-related texts,etc. This information can be either collected and stored on the serverin advance, or the client can do it (though not as efficiently).

Step 2. When the device with its dynamic parameters (movementparameters, duration, user preferences, etc.) comes into the picture,(a) the information collected about POIs is converted into acomprehensive story about the POI itself, taking into account saiddevice's dynamic parameters; (b) the set of “comprehensive stories”about POIs is converted into the connected guide being delivered to theuser, again based on the device's dynamic parameters. Technically, theserver may send the whole set of information about POIs along the routeto the device, and client device does the rest to create a connectedguide; however, the server may do some (if not all) processing of theinformation for the client, and in this case the client will receive theguide in pieces. Noting that the client behavior can change in a verydynamic way (speed, direction, changing routes), the server may providethe client with full processing of the raw information about a POI. Ifnot, the server performs some processing of the raw information anddelivers it in a shape such that it makes the work for creating a finalguide much easier. For example:

The server obtains the information about POIs from different sources,and creates a POI “story graph.” The story graph comprises nodescontaining pieces of the information regarding the POI which can beindependently delivered to the user (for example, paragraphs, orsentences, or small stories), and edges representing how the nodes canbe connected into the “comprehensive story” for the user. Building nodesfrom the raw info, and connecting them into the story graph is performedusing natural language understanding technologies. The story graph is astatic entity, i.e., it is independent from a specific device or users,allowing for creation of an exact “comprehensive story” about a POI veryfast based on the user dynamics and preferences. When the device withits dynamic parameters (movement params, duration, user preferences,etc.) comes into a range of a POI, said above comprehensive story aboutthe POI is created from this static graph based on the device dynamicparameters. As mentioned above, the POI comprehensive story can becreated on the server (where the device provides its parameters and getsback “comprehensive story” about POI ready to be delivered), oralternatively on the client (where the server just sends the story graphfor the POIs to the device).

It is to be understood that the above described embodiments are merelyillustrative of numerous and varied other embodiments which mayconstitute applications of the principles of the invention. Such otherembodiments may be readily devised by those skilled in the art withoutdeparting from the spirit or scope of this invention and it is ourintent they be deemed within the scope of our invention.

What is claimed is:
 1. A device of creating and delivering a customizedtravel guide for a user, wherein said guide corresponds to a route takenby the user, comprising: the electronic device includes a navigator, thedevice providing information about a geographical location of theelectronic device and a travel direction of the user, the geographicallocation of the electronic device being any location, the electronicdevice includes a speedometer, the speedometer providing information ofa speed of the user, said information of the user's speed being based onmovement of the electronic speedometer, wherein the geographicallocation of the electronic device, the speed of the electronic device,and the travel direction of the electronic device define electronicdevice movement parameters, the electronic device includes a displayproviding a topic of the guide to be selected, said topic includingarchitecture, history, nature, or current events relating to one or morepoints of interest (POIs) along the route taken by the user, a serverproviding information about said one or more points of interest alongthe route taken by the user, the server being connected to the displayand an audio system; a software of the server selecting publiclyavailable information related to the one or more POIs according to thedefined topic of the guide, said server transmitting the selectedpublicly available information related to the one or more POIs to thedisplay and the audio system, wherein the route taken by the user isestimated by the server software to create a predefined route from apoint A to a point B, wherein the route taken by the user is anestimated route based on a predictive analysis of the electronic devicemovement parameters, the electronic device creates a description foreach of the one or more POIs along the route taken by the user, eachsaid description being created based on the route taken by the user, theelectronic device movement parameters, and the selected publiclyavailable information about the one or more POIs, wherein eachdescription of each of the one or more POIs comprises a number of wordsequal to M×W, wherein M is a duration of time in minutes during whichsaid user is passing by each of the one or more POIs, wherein W is anumber of words per minute, calculating input values for M and W, theinput value for M being correlated to a device location and a devicemoving speed, the input value for W being determined by explicit userinput, and the electronic device delivers a description of each of theone or more POIs to the user for the duration of time, M.
 2. The deviceof claim 1, wherein the description is delivered via audio system. 3.The device of claim 1, wherein W is
 150. 4. The device of claim 1,wherein the delivering of the description occurs when the user is 100meters from each of the one or more POIs.